Software defined network lifecycle tracking and management

ABSTRACT

A device in an evolved packet core (EPC) which includes a processor and a memory. The processor effectuates operations including receiving, from one or more devices residing within a customer premise equipment (CPE) portion of a telecommunications network, sensor data associated with one or more customers and in response to receiving the sensor data, generating a data request for an ecosystem status for the CPE portion of the telecommunications network. The processor further effectuates operations including obtaining customer information for the one or more customers and creating an analytics environment, using the customer information, for the one or more customers. The processor further effectuates operations including performing, within the analytics environment, analytics on the sensor data to determine a state of the CPE portion of the telecommunications network for the one or more customers and in response to performing analytics on the sensor data, optimizing the telecommunications network.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority to, U.S.patent application Ser. No. 16/711,058, filed Dec. 11, 2019, entitled“Software Defined Network Lifecycle Tracking and Management,” the entirecontents of which are hereby incorporated herein by reference.

TECHNICAL FIELD

This disclosure is directed to a system and method for managingsoftware-defined networks, and, more specifically, to tracking andmanagement of software-defined networks as they evolve over time.

BACKGROUND

Communication networks have migrated from using specialized networkingequipment executing on dedicated hardware, like routers, firewalls, andgateways, to software defined networks (SDNs) executing as virtualizednetwork functions (VNF) in a cloud infrastructure. To provide a service,a set of VNFs may be instantiated on general-purpose hardware. Each VNFmay require one or more virtual machines (VMs) to be instantiated. Inturn, VMs may require various resources, such as memory, virtual centralprocessing units (vCPUs), and network interfaces or network interfacecards (NICs).

When the communications network implements fifth generation cellularnetwork technology (5G), utilizing a Control and User Plane Separation(CUPS) is important to 5G networks because it allows operators toseparate the evolved packet core (EPC) into a control plane that canreside in a centralized location, for example the middle of the country,and for the user plane to be placed closer to the application it issupporting. This type of separation may be helpful for applications suchas, the connected car. In that scenario, a network operator can placethe EPC user plane in a data center in a city so that it is closer tothe application and therefore reduces the latency. This scenario alsoworks well for high-bandwidth applications like video. Because the coreuser plane is located closer to the end user the operator does not haveto backhaul traffic all the way to central hub and therefore providesmore efficient processing.

This background information is provided to reveal information believedby the applicant to be of possible relevance. No admission isnecessarily intended, nor should be construed, that any of the precedinginformation constitutes prior art.

SUMMARY

There is a need to provide a CUPS architecture that can collect data foran associated communications network dynamically, analyze networkparameters, and adjust aspects of the communications network based onthe analysis of network parameters. Disclosed herein is a data captureand simulation engine that may reside in an evolved packet core (EPC)hereby referred to as the Core Simulation Tool (CST). The CST cancollect data from a RAN, IoT sensors, or other devices and use EPCnetwork elements to perform analysis and simulations on the collecteddata, combine the collected data with additional information, anddynamically change network parameters in response to network conditions.

The present disclosure is directed to a device in an evolved packet core(EPC) having a processor and a memory coupled with the processor. Theprocessor effectuates operations including receiving, from one or moredevices residing within a customer premise equipment (CPE) portion of atelecommunications network, sensor data associated with one or morecustomers. The processor further effectuates operations including inresponse to receiving the sensor data, generating a data request for anecosystem status for the CPE portion of the telecommunications network.The processor further effectuates operations including obtainingcustomer information for the one or more customers. The processorfurther effectuates operations including creating an analyticsenvironment, using the customer information, for the one or morecustomers. The processor further effectuates operations includingperforming, within the analytics environment, analytics on the sensordata to determine a state of the CPE portion of the telecommunicationsnetwork for the one or more customers. The processor further effectuatesoperations including in response to performing analytics on the sensordata, optimizing the telecommunications network.

The present disclosure is directed to a computer-implemented method. Thecomputer-implemented method includes receiving, from one or more devicesresiding within a customer premise equipment (CPE) portion of atelecommunications network, sensor data associated with one or morecustomers. The computer-implemented method further includes in responseto receiving the sensor data, generating a data request for an ecosystemstatus for the CPE portion of the telecommunications network. Thecomputer-implemented method further includes obtaining customerinformation for the one or more customers. The computer-implementedmethod further includes creating an analytics environment, using thecustomer information, for the one or more customers. Thecomputer-implemented method further includes performing, within theanalytics environment, analytics on the sensor data to determine a stateof the CPE portion of the telecommunications network for the one or morecustomers. The computer-implemented method further includes in responseto performing analytics on the sensor data, optimizing thetelecommunications network.

The present disclosure is directed to a computer-readable storage mediumstoring executable instructions that when executed by a computing devicecause said computing device to effectuate operations includingreceiving, from one or more devices residing within a customer premiseequipment (CPE) portion of a telecommunications network, sensor dataassociated with one or more customers. Operations further include inresponse to receiving the sensor data, generating a data request for anecosystem status for the CPE portion of the telecommunications network.Operations further include obtaining customer information for the one ormore customers. Operations further include creating an analyticsenvironment, using the customer information, for the one or morecustomers. Operations further include performing, within the analyticsenvironment, analytics on the sensor data to determine a state of theCPE portion of the telecommunications network for the one or morecustomers. Operations further include in response to performinganalytics on the sensor data, optimizing the telecommunications network.

The present disclosure is directed to a device in an evolved packet core(EPC) having a processor and a memory coupled with the processor. Theprocessor effectuates operations including deploying a simulation toolwithin a telecommunications network, wherein the simulation tool is avirtual network function within the telecommunications network;receiving sensor data associated with one or more customer premiseequipment (CPE) devices of a CPE network of a plurality of CPE networkswithin the telecommunications network; performing analytics on thesensor data of the one or more CPE devices within the CPE network; basedon the performing of analytics on the sensor data, determining a statusof the CPE network; and based on the status of the CPE network,optimizing the CPE network.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the herein described telecommunications network and systemsand methods are described more fully with reference to the accompanyingdrawings, which provide examples. In the following description, forpurposes of explanation, numerous specific details are set forth inorder to provide an understanding of the variations in implementing thedisclosed technology. However, the instant disclosure may take manydifferent forms and should not be construed as limited to the examplesset forth herein. Where practical, like numbers refer to like elementsthroughout.

FIG. 1 is a block diagram of an exemplary operating environment inaccordance with the present disclosure;

FIG. 2A is a flowchart of an exemplary method of operation for thearchitecture described in FIG. 1;

FIG. 2B is a flowchart of an exemplary method of operation for thearchitecture described in FIG. 1;

FIG. 3 is a schematic of an exemplary network device;

FIG. 4 depicts an exemplary communication system that provide wirelesstelecommunication services over wireless communication networks withwhich edge computing node may communicate;

FIG. 5 depicts an exemplary communication system that provide wirelesstelecommunication services over wireless communication networks withwhich edge computing node may communicate;

FIG. 6 is a diagram of an exemplary telecommunications system in whichthe disclosed methods and processes may be implemented with which edgecomputing node may communicate;

FIG. 7 is an example system diagram of a radio access network and a corenetwork with which edge computing node may communicate;

FIG. 8 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a general packet radioservice (GPRS) network, with which edge computing node may communicate;

FIG. 9 illustrates an exemplary architecture of a GPRS network withwhich edge computing node may communicate; and

FIG. 10 is a block diagram of an exemplary public land mobile network(PLMN) with which edge computing node may communicate.

DETAILED DESCRIPTION

The internet of things (IoT) may be described as a computing conceptdescribing an idea of physical devices (computing devices, sensors,mechanical and digital machines, etc.) being connected to the Internetand being able to identify themselves to other devices using uniqueidentifiers (UIDs). The physical devices can use their UID andconnection to the Internet to transfer data (IoT data) without requiringhuman-to-human or human-to-computer interaction.

Conventionally, IoT data is extracted from various IoT devices (e.g.,smart meters, commercial security systems, traffic monitoring systems,weather monitoring systems, vehicles, smart home devices and sensors),which may utilize different protocols. The extracted IoT data can beforwarded to various gateways for protocol translation where the IoTdata of the various sensors are translated and compiled to gain insightinto an ecosystem (e.g., a communications network, building, system,device, etc.). The gateways receiving the IoT data can forward the IoTdata to a Cloud database (e.g., Microsoft Azure SQL Database, Amazon WebServices Database, Google Cloud SQL Database, etc.) for processing. Forexample, the IoT data can be related to a communications network havingan Evolved Packet Core (EPC) that can forward the IoT data to the Clouddatabase. This processing typically includes extraction, transformationand loading of data into another database(s), which can be accessed foranalysis. Usually, the processing of the collected IoT data takes placeoutside of the EPC. However, processing IoT data outside of the EPCfails to reflect data associated with individual IoT sensors,information associated with specific cell sites, authentication vectorsprovided to a Mobility Management Entity and location based services(LBS) information associated with each of the IoT sensors, as well asperformance aspects and security information, which only exists withinthe EPC core of a carrier and can be obtained faster from associatednetwork elements. Analyzing an ecosystem with incomplete information canlead to an incomplete assessment of the state or status of theecosystem. Accordingly, providing an analytics environment within theEPC that can process the IoT data, as well as the data associated withindividual IoT sensors, would be beneficial by creating greaterefficiencies, performance, security, and control by the network carrier.In addition, providing an analytics environment within the EPC that canprocess location information for each of the IoT sensors, performanceaspects, and security information would also be beneficial.

The present disclosure includes new and novel network analysis andmanagement tool (core simulation tool) that can collect IoT data and RANdata, as well as a software defined engine (SDE) that can be used tocreate an analytics environment within the EPC. While the system andmethod will be described herein in an exemplary configuration in whichthe core simulation tool (CST) operates in an EPC of a 5G network, thesystem and method of the present disclosure can be deployed at otherlocations within a network and may be implemented in a non-5G CUPSenvironment.

On a customer premise side, software-defined network equipment may hostmultiple VNFs which will be referred to as a user plane SD-WAN gateway(U-SDWAN). The U-SDWAN gateway may be managed by a control plane SDWANorchestrator (C-SDWAN) in a 5G core network. The U-SDWAN may belogically placed in communication with user plane of the serving gateway(U-SGW) and the user plane of the packet data network gateway (U-PGW) atthe customer premises. The U-SDWAN residing in the customer premises maycommunicate with other U-SDWANs at other customer locations. MultipleVNFs may be established in each U-SDWAN as needed or desired.

On a carrier network side, corresponding control planes may form a partof the Evolved Packet Core (EPC), which may, for example, include thecontrol plane Mobility Management Entity (C-MME), control plane of theserving gateway (C-SGW), and the control plane of the packet datanetwork gateway (C-PGW).

The U-SDWAN may route packets originating from the mobile or fixed 5GRAN to the appropriate destination. In operation in one embodiment, anIoT device may connect with the 5G RAN, via a wired connection or awireless connection, and establish a session with the enterprise networkthrough the EPC by being authenticated by the control plane C-MME andthen establishing a session with the C-SGW and C-PGW. The IoT device maythen establish a session with the U-SGW. The U-SGW may forward the datato the U-SDWAN being managed by C-SDWAN. The U-SDWAN may establish oneor more user plane VNFs. The U-VNF may route the packets to entitiesoutside of the carrier network or to multiple customer locations. TheC-SDWAN may provide the policy considerations derived from theenterprise network with intelligence in the U-SDWAN routing the packetsthrough various possible connections. The C-SDWAN may also communicatewith other orchestrators outside of the carrier environment andinterface with enterprise customers via an external web interface. TheC-SDWAN and the U-SDWAN may communicate to update policies as requestedby the network or the customer.

As non-limiting example, the analytics environment within the EPC mayinclude analytical databases and associated tools. The analyticsenvironment can analyze IoT data from sensors, data associated withindividual IoT sensors, a location of each of the IoT sensors, a RadioAccess Network (RAN), performance aspects of the RAN ortelecommunications network in general, and security information todetermine a state of the communications network, and dynamically adjustaspects of the communications network based on the determined state ofthe communications network. The core simulation tool (CST) may be placedwithin the EPC and may be implemented as a user plane Virtual NetworkFunction (VNF) (uCST) that may be placed within a customer premises.

FIG. 1 shows an exemplary systems architecture 10 of a 5G CUPSarchitecture with a network portion 12 and a customer premise equipment(CPE) portion 30. Consistent with the CUPS architecture, the networkportion 12 includes one or more control planes having various componentsand the CPE portion 30 includes a user plane having various components.

While the network portion 12 is described in further detail below, theblock diagram of FIG. 1 shows the exemplary network portion 12 as it maybe configured in accordance with the present disclosure. On a carriernetwork side of systems architecture 10 (network portion 12),corresponding control planes may form a network carrier EPC 14. Withinthe EPC 14, there is shown a control plane of the mobility managemententity (MME) (C-MME 43), a control plane of the PGW (C-PGW 45), acontrol plane of the SGW (C-SGW 47), and a core simulation tool (CST) 50that includes a dynamic software defined engine for IoT analytics(DSDE-IA) 51. The EPC 14 interacts with the enterprise network 20, whichmay be a private or shared network operated by a network carrier or byan enterprise customer. The EPC 14 may connect with the Internet 22 athrough a direct connection or through an internet service provider.Provisioning of the EPC 14 and IoT sensors 32 may be performed by theenterprise customer by accessing the enterprise level provisioninginterface 24 accessed through the to the Internet 22 a. The provisioningmay also be done by the network carrier on behalf of an enterprisecustomer. Note that the Internet portions 22 a and 22 b of FIG. 1 may beconsidered to be part of the global Internet; however, Internet portions22 a and 22 b are referenced separately herein only for the conveniencein describing interface to the Internet with respect to the networkportion 12 and the CPE portion 30 of system 10, and the recognition thatactual Internet access points may differ between those portions.

There is also shown a C-SDWAN 16. The C-SDWAN 16 may, among otherfunctions, control the policies to be implemented by the network carrierglobally or geographically or by individual enterprise customers. TheC-SDWAN 16 may be provisioned with provisioning data stored in aprovisioning database 18. The C-SDWAN 16 may thus be configured to formpart of the EPC 14 or to closely interact with the EPC 14 on the carriernetwork portion 12. Likewise, the C-SDWAN 16 may be configured tointeract with the enterprise customer network 20, the enterprise levelprovisioning interface 24 and the provisioning database 18. With theC-SDWAN 16 being software-defined, multiple instances of the controlplane WAN may be implemented for multiple-enterprise customers orindividual customers being serviced by the network carrier.

Turning to the CPE portion 30 of FIG. 1, there is shown the user planescorresponding to the control planes discussed above. There is a U-PGW36, a U-SGW 38, and a U-SDWAN 40. Each of the U-PGW 36, U-SGW 38, andthe U-SDWAN 40 may be in communication with each other, directly orindirectly through one of the interfaces as shown in FIG. 1. The U-PGW26 and the U-SGW 38 may functionally operate as is known by thoseskilled in the art of telecommunications using the 5G CUPS architecture.For example, the U-PGW 36 may interface and exchange data with anenterprise wide area network, shown as Enterprise WAN 44. That U-PGW 36may thus provide a gateway to and from the Enterprise WAN 44 from and tothe 5G Radio Access Network (RAN) 34. One or more mobile devices 32 mayalso access the 5G RAN 34.

There may be one or more U-SDWANs 40 in any architecture. Enterprisesmay configure the U-SDWANs 40 to meet specific or personalizedprocessing requirements. For example, different U-SDWANs 40 may operateusing different policies received from the C-SDWAN 16 described below.There may be different policies for different devices, users, or classesof users. Within each U-SDWAN, one or more U-VNFs may be instantiated.

There may also be a communication interface between the 5G RAN 34 andthe internet 22 b. As such, there is an established communication pathbetween IoT devices 32, the enterprise WAN 44 and the Internet 22 b. Inthis example, the enterprise WAN 44 may be a traditional enterprise WANconnecting multiple customer sites through a wide area network. It maybe a software-defined WAN which connects enterprise networks includingbranch offices and data centers over large geographic distances. Thoseconnections may, for example, use broadband internet, 4G, Long-TermEvolution (LTE) or Multiprotocol Label Switching (MPLS) connections.With reference to the U-SDWAN 40, there are shown exemplary connectionsto the 5G RAN 34, the EPC 14 and, directly or indirectly, to the C-SDWAN16, and provisioning database 18.

The CST 50 may collect data from the 5G RAN 34, IoT devices 32, andother devices in order to perform an integrated and aggregated analysisusing, for example, authentication vectors in the MME, locationinformation in the LBS servers, policy parameters in a Policy andCharging Rules Function (PCRF), evolved Node B (eNodeB) information,other information contained in a Home Subscriber Server (HSS) associatedwith a given network element. The analysis performed by the CST 50, aswell as simulations may be performed inside of the EPC 14. In 5Gnetworks, a user plane Virtual Network Function (VNF) (uCST) 55 may alsobe employed, which may be created and controlled via the CST 50. TheuCST 55 may reside on a customer premises. In addition, more than oneuCST 55 may be employed. The uCST 55 may be used to collect the datalocally to perform a customer specific analysis, as well as forward thecollected data to the CST 50 in order to perform the integrated andaggregated analysis. The uCST 55 may be deployed anywhere in the 5Gnetwork when authorized by the CST 50, as well as a customer when theuCST 55 resides on a customer premises.

In an exemplary instance where the CST 50 analyses data collected fromIoT devices 32, data produced by the IoT devices 32 (e.g., smart meters,commercial security systems, traffic monitoring systems, weathermonitoring systems, vehicles, smart home devices and sensors) may becollected. The collected data may be forwarded from the IoT devices 32to a sensor gateway (not shown) within the customer premises, whichforwards the collected data to and from various network elements thatreside throughout the 5G network. The sensor gateway may forward thecollected data to an LTE RAN (discussed below in respect to FIG. 4). Thecollected data may be received by the C-MME 43 within the EPC 14, whichforwards the collected data to the CST 50, which also resides within theEPC 14. The DSDE-IA 51 may be implemented as a virtual machine. TheDSDE-IA 51 may be used to create one or more analytics environments fora customer associated with the customer premises. The DSDE-IA 51 may beused to create each of the one or more analytics environments using anassociated hypervisor. The DSDE-IA 51 may host a database (e.g., aHadoop database) and include software (e.g., analytics programs) whichmay be used to map the collected data and reduce the collected data intobusiness objects, functional tables, or dimensional tables. While theCST 50 and associated DSDE-IA 51 may be considered an element of the EPC14, the one or more analytics environments and collected data containedwithin the DSDE-IA 51 can be accessed from network elements residingoutside of the EPC 14. The DSDE-IA 51 may generate a data request (e.g.,an ecosystem status request for CPE portion 30), dynamically, inresponse to the collected data, systems conditions, data requirements ornetwork elements queries conducted by the DSDE-IA 51. The DSDE-IA 51 mayoutput one or more reports in response to the data request to provideinsight into a CPE portion 30 or network portion 12, via an ApplicationsProgramming Interface (API). The data request may be forwarded tovarious network elements (eNodeBs, MMES, etc.) or IoT devices 32. TheDSDE-IA 51 may also dynamically issue one or more commands in responseto the collected data, information data capture requirements or systemsconditions to resolve issues within the customer premises or the 5Gnetwork.

A system hosting the customer API may include a customer DSDE-IA“(C-DSDE-IA) (not shown) which is able interface with the DSDE-IA 51 ina secure manner. The C-DSDE-IA may be used to interface with customersoutside of the network. For example, a customer may utilize a webinterface that communicates with the C-DSDE-IA to “provision” IoTdevices 32 and uCST 55, as well as supporting information such as timeof day, particular users, relevant security profiles, authorizations,data forwarding and receipt polices, etc. The DSDE-IA 51 may alsoinclude a security engine which may be used for provisioning,authentication and authorization of communication received from thecustomer premises. The security engine may access a provisioningdatabase stored by the DSDE-IA 51 to retrieve customer profiles. TheDSDE-IA 51 may include an analytics programming engine (APE) which hostsvarious analytics programs (e.g., Tableau, PowerBi, etc.), as well asinterface with APEs residing outside of the EPC 14 (e.g., IBM Watson).

Accordingly, in response to receiving sensor data from IoT devices, aswell as data associated with individual IoT sensors, locationinformation associated with each of the IoT sensors, performance aspectsand security information from the uCST 55, the DSDE-IA 51 may generate adata request triggering an analysis by one or more analytics programs ofthe DSDE-IA 51 to determine a state or status of a customer ecosystem ornetwork in general. For example, a manufacturer may utilize temperaturesensors to measure temperature in a designated portion of a plant. TheuCST 55 residing at the plant may interface with the temperaturesensors, via a wired connection or a wireless connection, e.g., WiFi,LTE, 5GNR, etc. The uCST 55 may forward the sensor data received fromthe temperature sensors to the CST 50 for integration. The uCST 55 mayalso request data (e.g., LBS information) associated with thetemperature sensors and integrate the temperature data provided by thetemperature sensors with received LBS information. The uCST 55 may alsoreceive data from, for example, a security sensor located near a giventemperature sensor. Accordingly, the uCST 55 can then aggregate LBSinformation, security data and temperature data in a record, which maybe stored locally by the uCST 55 or forwarded to the CST 50. The CST 50can provide information associated with the state or status of theecosystem to the customer or adjust aspects of the network portion 12 orthe CPE portion 30 based on the determined state or status of theecosystem based on the received data and associated customer information(e.g., subscriber information, device information, location information,and security information). For example, the analysis of IoT sensor dataincluding location information and individual IoT sensor data by the CST50 can indicate network coverage gaps at designated locations within acustomer ecosystem (e.g., CPE 30) or the network, in general. Inresponse to the determination of network coverage gaps, the CST 50 mayperform network optimizations by dynamically adjusting networkperformance parameters of the core network, providing a service requestto the network carrier requesting installation of one or more macrosites or small cells, or to spin up/down one or more new gateways atdesignated locations at the customer premises or another part of thenetwork, as needed, to address determined network coverage gaps. Inaddition to network coverage gaps, the network may be optimized based onusage pattern changes or in response to overloads. In another example,the analysis of IoT sensor data including location information andindividual IoT sensor data can indicate poor network performance for aspecified portion of the customer ecosystem. In response to thedetermination poor network performance for a specified portion of thecustomer ecosystem, the CST 50 may dynamically adjust performanceaspects within the network portion 12 or the CPE portion 30 to resolvethe determined performance issues. Optimizing may including performingactions that reduce latency, increase throughput, or reduce errors,among other things.

In an exemplary instance where the CST 50 performs network data captureand analyses, network data may be collected by a network carrier RAN andthe network data may be sent from the network carrier RAN to the CST 50,which resides in the EPC 14. Additional data (e.g., records from theuCST 55 for integration, RAN records indicating connections betweeneNodeBs and sensors, sensor priority data, network performance data,network congestion data, etc.) may be received by the CST 50 from theC-MME 43, one or more eNodeBs or other network elements. The CST 50 canaccess network performance data, which may be stored in a CST networkperformance data repository. The DSDE-IA 51 may include an analyticsprogramming engine (APE) which hosts various analytics programs (e.g.,Tableau, PowerBi, etc.). The APE may be used by the CST 50 to performLTE simulations using the network data and additional data to predicthow a set of circumstances or change(s) to the network may affectnetwork performance. For example, would adding sensors throughout amanufacturing plant adversely affect network performance for the entirenetwork, adversely affect network performance for the manufacturingplant network or portion thereof, have no effect on network performance,etc.

The CST 50 may acquire data from the DSDE-IA 51 via a data request(e.g., a network performance request), dynamically, in response tosystems conditions or data requirements. The network performance datarequest may be forwarded to various network elements (eNodeBs, MMES,etc.) or IoT devices 32. The DSDE-IA 51 may dynamically generate datarequests in response to information data capture requirements or systemsconditions associated with the network performance request. The CST 50may dynamically adjust LTE simulations upon receipt of new network datafrom the RAN or other network elements.

To obtain insight into network performance, users can access/interfacewith the CST 50 via an API (e.g., a web-based system). The DSDE-IA 51may be used to create each of the one or more analytics environments.The DSDE-IA 51 may include software (e.g., analytics programs) which canbe used to analyze network performance based on the network data andadditional data. Data and performance parameters used for simulationsand analysis by the CST 50 may be changed dynamically in response tonetwork conditions and external parameters. The DSDE-IA 51 may obtaindata from outside the EPC 14 or a network to obtain a more completepicture of network carrier operations. The CST 50 may dynamicallygenerate reports and on-demand reports related to operation of a network(e.g., network performance). The CST 50 may also generate an alertindicating a network issue(s), which can be sent to user via the API. Insome instances, the CST 50 may dynamically adjust performance aspectswithin the network portion 12 or the CPE portion 30 to resolve thenetwork issue(s) by, for example, directing uCST 55 to stop collectingdata from certain sensors or direct certain eNodeBs to turn down poweror to hand off cell service to another nearby eNodeB. The CST 50 mayalso interface with various Operations Support Systems (OSS) systems inorder to provide predictive analytics to the various OSS systems, whichcan be used to manage an associated network (e.g., network inventory,service provisioning, network configuration and fault management).

An exemplary operational flowchart in accordance with a method of thepresent disclosure is illustrated in FIG. 2A. At block 205, a coresimulation tool (CST) 50, may be deployed within network carrier EvolvedPacket Core (EPC) 14. At block 210, the CST 50 may receive IoT data fromone or more IoT devices 32. At block 215, the CST 50 may receiveadditional data (e.g., data associated with individual IoT devices 32and location information associated with each of the IoT devices 32). Atblock 220, the CST 50 may generate a data request. For example, the datarequest can be a request to obtain cell coverage data for the customerpremises. At block 225, the CST 50 may access customer information(e.g., subscriber information, device information, location information,and security information), as well as customer profiles of the customerthat are relevant to the data request. At block 230, the CST 50 mayutilize analytics programs within the CST 50 to map and reduce thecollected data, as well as determine a state or status of a customerecosystem. At block 235, the CST 50 may provide the customer with areport of the state or status of the customer ecosystem or optimizeoperations of the network in response to the determination of the stateor status of the customer ecosystem.

An exemplary operational flowchart in accordance with a method of thepresent disclosure is illustrated in FIG. 2B. At block 250, a coresimulation tool (CST) 50 may be deployed at within network carrierEvolved Packet Core (EPC) 14. At block 255, the CST 50 may receivenetwork data from a network carrier RAN 34. At block 260, the CST 50 mayreceive additional network data from eNodeBs, MMES, or other networkdevices. At block 265, the CST 50 may receive perform an LTE simulationusing the network data and additional network data. At block 270, theCST 50 may utilize analytics programs within the CST 50 to determinewhether network performance issues exist (e.g., devices failing toconnect to the network carrier RAN 34, slow data transmission or dataprocessing due to network congestion, backbone data circuitmalfunctions, etc.) based on the received network data and additionalnetwork data. At block 275, if the CST 50 determines that networkperformance issues exist the method proceeds to block 285 where the CST50 may provide a report about the network performance via an API. Inresponse to network performance issues, the CST 50 may also generate analert indicating the existence of network performance issues. Inresponse to network performance issues, the CST 50 may also cause anetwork performance optimization to occur in order to rectify thenetwork performance issues.

If the CST 50 determines that network performance issues do not exist,the method proceeds to block 280 where the CST 50 may determine whethernew network data or new additional data has been received. If newnetwork data or new additional data has been received, the methodreturns to block 265. If new network data or new additional data has notbeen received, the method return to block 255.

FIG. 3 is a block diagram of network device 300 that may be connected toor comprise a component of edge computing node 104 or connected to edgecomputing node 104 via a network (e.g., core network 12 of FIG. 1).Network device 300 may comprise hardware or a combination of hardwareand software. The functionality to facilitate telecommunications via atelecommunications network may reside in one or combination of networkdevices 300. Network device 300 depicted in FIG. 3 may represent orperform functionality of an appropriate network device 300, orcombination of network devices 300, such as, for example, a component orvarious components of a cellular broadcast system wireless network, aprocessor, a server, a gateway, a node, a mobile switching center (MSC),a short message service center (SMSC), an ALFS, a gateway mobilelocation center (GMLC), a radio access network (RAN), a serving mobilelocation center (SMLC), or the like, or any appropriate combinationthereof. It is emphasized that the block diagram depicted in FIG. 3 isexemplary and not intended to imply a limitation to a specificimplementation or configuration. Thus, network device 300 may beimplemented in a single device or multiple devices (e.g., single serveror multiple servers, single gateway or multiple gateways, singlecontroller or multiple controllers). Multiple network entities may bedistributed or centrally located. Multiple network entities maycommunicate wirelessly, via hard wire, or any appropriate combinationthereof.

Network device 300 may comprise a processor 302 and a memory 304 coupledto processor 302. Memory 304 may contain executable instructions that,when executed by processor 302, cause processor 302 to effectuateoperations associated with mapping wireless signal strength.

In addition to processor 302 and memory 304, network device 300 mayinclude an input/output system 306. Processor 302, memory 304, andinput/output system 306 may be coupled together (coupling not shown inFIG. 3) to allow communications therebetween. Each portion of networkdevice 300 may comprise circuitry for performing functions associatedwith each respective portion. Thus, each portion may comprise hardware,or a combination of hardware and software. Input/output system 306 maybe capable of receiving or providing information from or to acommunications device or other network entities configured fortelecommunications. For example, input/output system 306 may include awireless communications (e.g., 3G/4G/GPS) card. Input/output system 306may be capable of receiving or sending video information, audioinformation, control information, image information, data, or anycombination thereof. Input/output system 306 may be capable oftransferring information with network device 300. In variousconfigurations, input/output system 306 may receive or provideinformation via any appropriate means, such as, for example, opticalmeans (e.g., infrared), electromagnetic means (e.g., RF, Wi-Fi,Bluetooth®, ZigBee®), acoustic means (e.g., speaker, microphone,ultrasonic receiver, ultrasonic transmitter), or a combination thereof.In an example configuration, input/output system 306 may comprise aWi-Fi finder, a two-way GPS chipset or equivalent, or the like, or acombination thereof.

Input/output system 306 of network device 300 also may contain acommunication connection 308 that allows network device 300 tocommunicate with other devices, network entities, or the like.Communication connection 308 may comprise communication media.Communication media typically embody computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. By way of example, and not limitation,communication media may include wired media such as a wired network ordirect-wired connection, or wireless media such as acoustic, RF,infrared, or other wireless media. The term computer-readable media asused herein includes both storage media and communication media.Input/output system 306 also may include an input device 310 such askeyboard, mouse, pen, voice input device, or touch input device.Input/output system 306 may also include an output device 312, such as adisplay, speakers, or a printer.

Processor 302 may be capable of performing functions associated withtelecommunications, such as functions for processing broadcast messages,as described herein. For example, processor 302 may be capable of, inconjunction with any other portion of network device 300, determining atype of broadcast message and acting according to the broadcast messagetype or content, as described herein.

Memory 304 of network device 300 may comprise a storage medium having aconcrete, tangible, physical structure. As is known, a signal does nothave a concrete, tangible, physical structure. Memory 304, as well asany computer-readable storage medium described herein, is not to beconstrued as a signal. Memory 304, as well as any computer-readablestorage medium described herein, is not to be construed as a transientsignal. Memory 304, as well as any computer-readable storage mediumdescribed herein, is not to be construed as a propagating signal. Memory304, as well as any computer-readable storage medium described herein,is to be construed as an article of manufacture.

Memory 304 may store any information utilized in conjunction withtelecommunications. Depending upon the exact configuration or type ofprocessor, memory 304 may include a volatile storage 314 (such as sometypes of RAM), a nonvolatile storage 316 (such as ROM, flash memory), ora combination thereof. Memory 304 may include additional storage (e.g.,a removable storage 318 or a nonremovable storage 320) including, forexample, tape, flash memory, smart cards, CD-ROM, DVD, or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, USB-compatible memory, or any othermedium that can be used to store information and that can be accessed bynetwork device 300. Memory 304 may comprise executable instructionsthat, when executed by processor 302, cause processor 302 to effectuateoperations to map signal strengths in an area of interest.

FIG. 4 illustrates a functional block diagram depicting one example ofan LTE-EPS network architecture 400 related to the current disclosure.In particular, the network architecture 400 disclosed herein is referredto as a modified LTE-EPS architecture 400 to distinguish it from atraditional LTE-EPS architecture.

An example modified LTE-EPS architecture 400 is based at least in parton standards developed by the 3rd Generation Partnership Project (3GPP),with information available at www.3gpp.org. In one embodiment, theLTE-EPS network architecture 400 includes an access network 402, a corenetwork 404, e.g., an EPC or Common BackBone (CBB) and one or moreexternal networks 406, sometimes referred to as PDN or peer entities.Different external networks 406 can be distinguished from each other bya respective network identifier, e.g., a label according to DNS namingconventions describing an access point to the PDN. Such labels can bereferred to as Access Point Names (APN). External networks 406 caninclude one or more trusted and non-trusted external networks such as aninternet protocol (IP) network 408, an IP multimedia subsystem (IMS)network 410, and other networks 412, such as a service network, acorporate network, or the like.

Access network 402 can include an LTE network architecture sometimesreferred to as Evolved Universal mobile Telecommunication systemTerrestrial Radio Access (E UTRA) and evolved UMTS Terrestrial RadioAccess Network (E-UTRAN). Broadly, access network 402 can include one ormore communication devices, commonly referred to as UE 414, and one ormore wireless access nodes, or base stations 416 a, 416 b. Duringnetwork operations, at least one base station 416 communicates directlywith UE 414. Base station 416 can be an evolved Node B (eNodeB), withwhich UE 414 communicates over the air and wirelessly. UEs 414 caninclude, without limitation, wireless devices, e.g., satellitecommunication systems, portable digital assistants (PDAs), laptopcomputers, tablet devices, Internet-of-things (IoT) devices, and othermobile devices (e.g., cellular telephones, smart appliances, and so on).UEs 414 can connect to eNBs 416 when UE 414 is within range according toa corresponding wireless communication technology.

UE 414 generally runs one or more applications that engage in a transferof packets between UE 414 and one or more external networks 406. Suchpacket transfers can include one of downlink packet transfers fromexternal network 406 to UE 414, uplink packet transfers from UE 414 toexternal network 406 or combinations of uplink and downlink packettransfers. Applications can include, without limitation, web browsing,VoIP, streaming media, and the like. Each application can pose differentQuality of Service (QoS) requirements on a respective packet transfer.Different packet transfers can be served by different bearers withincore network 404, e.g., according to parameters, such as the QoS.

Core network 404 uses a concept of bearers, e.g., EPS bearers, to routepackets, e.g., IP traffic, between a particular gateway in core network404 and UE 414. A bearer refers generally to an IP packet flow with adefined QoS between the particular gateway and UE 414. Access network402, e.g., E UTRAN, and core network 404 together set up and releasebearers as required by the various applications. Bearers can beclassified in at least two different categories: (i) minimum guaranteedbit rate bearers, e.g., for applications, such as VoIP; and (ii)non-guaranteed bit rate bearers that do not require guarantee bit rate,e.g., for applications, such as web browsing.

In one embodiment, the core network 404 includes various networkentities, such as MME 418, SGW 420, Home Subscriber Server (HSS) 422,Policy and Charging Rules Function (PCRF) 424 and PGW 426. In oneembodiment, MME 418 comprises a control node performing a controlsignaling between various equipment and devices in access network 402and core network 404. The protocols running between UE 414 and corenetwork 404 are generally known as Non-Access Stratum (NAS) protocols.

For illustration purposes only, the terms MME 418, SGW 420, HSS 422 andPGW 426, and so on, can be server devices, but may be referred to in thesubject disclosure without the word “server.” It is also understood thatany form of such servers can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as bearer paths orinterfaces are terms that can include features, methodologies, or fieldsthat may be described in whole or in part by standards bodies such asthe 3GPP. It is further noted that some or all embodiments of thesubject disclosure may in whole or in part modify, supplement, orotherwise supersede final or proposed standards published andpromulgated by 3GPP.

According to traditional implementations of LTE-EPS architectures, SGW420 routes and forwards all user data packets. SGW 420 also acts as amobility anchor for user plane operation during handovers between basestations, e.g., during a handover from first eNB 416 a to second eNB 416b as may be the result of UE 414 moving from one area of coverage, e.g.,cell, to another. SGW 420 can also terminate a downlink data path, e.g.,from external network 406 to UE 414 in an idle state and trigger apaging operation when downlink data arrives for UE 414. SGW 420 can alsobe configured to manage and store a context for UE 414, e.g., includingone or more of parameters of the IP bearer service and network internalrouting information. In addition, SGW 420 can perform administrativefunctions, e.g., in a visited network, such as collecting informationfor charging (e.g., the volume of data sent to or received from theuser), or replicate user traffic, e.g., to support a lawfulinterception. SGW 420 also serves as the mobility anchor forinterworking with other 3GPP technologies such as universal mobiletelecommunication system (UMTS).

At any given time, UE 414 is generally in one of three different states:detached, idle, or active. The detached state is typically a transitorystate in which UE 414 is powered on but is engaged in a process ofsearching and registering with network 402. In the active state, UE 414is registered with access network 402 and has established a wirelessconnection, e.g., radio resource control (RRC) connection, with eNB 416.Whether UE 414 is in an active state can depend on the state of a packetdata session, and whether there is an active packet data session. In theidle state, UE 414 is generally in a power conservation state in whichUE 414 typically does not communicate packets. When UE 414 is idle, SGW420 can terminate a downlink data path, e.g., from one peer entity 406,and triggers paging of UE 414 when data arrives for UE 414. If UE 414responds to the page, SGW 420 can forward the IP packet to eNB 416 a.

HSS 422 can manage subscription-related information for a user of UE414. For example, HSS 422 can store information such as authorization ofthe user, security requirements for the user, quality of service (QoS)requirements for the user, etc. HSS 422 can also hold information aboutexternal networks 406 to which the user can connect, e.g., in the formof an APN of external networks 406. For example, MME 418 can communicatewith HSS 422 to determine if UE 414 is authorized to establish a call,e.g., a voice over IP (VoIP) call before the call is established.

PCRF 424 can perform QoS management functions and policy control. PCRF424 is responsible for policy control decision-making, as well as forcontrolling the flow-based charging functionalities in a policy controlenforcement function (PCEF), which resides in PGW 426. PCRF 424 providesthe QoS authorization, e.g., QoS class identifier and bit rates thatdecide how a certain data flow will be treated in the PCEF and ensuresthat this is in accordance with the user's subscription profile.

PGW 426 can provide connectivity between the UE 414 and one or more ofthe external networks 406. In illustrative network architecture 400, PGW426 can be responsible for IP address allocation for UE 414, as well asone or more of QoS enforcement and flow-based charging, e.g., accordingto rules from the PCRF 424. PGW 426 is also typically responsible forfiltering downlink user IP packets into the different QoS-based bearers.In at least some embodiments, such filtering can be performed based ontraffic flow templates. PGW 426 can also perform QoS enforcement, e.g.,for guaranteed bit rate bearers. PGW 426 also serves as a mobilityanchor for interworking with non-3GPP technologies such as CDMA2000.

Within access network 402 and core network 404 there may be variousbearer paths/interfaces, e.g., represented by solid lines 428 and 430.Some of the bearer paths can be referred to by a specific label. Forexample, solid line 428 can be considered an S1-U bearer and solid line432 can be considered an S5/S8 bearer according to LTE-EPS architecturestandards. Without limitation, reference to various interfaces, such asS1, X2, S5, S8, S11 refer to EPS interfaces. In some instances, suchinterface designations are combined with a suffix, e.g., a “U” or a “C”to signify whether the interface relates to a “User plane” or a “Controlplane.” In addition, the core network 404 can include various signalingbearer paths/interfaces, e.g., control plane paths/interfacesrepresented by dashed lines 430, 434, 436, and 438. Some of thesignaling bearer paths may be referred to by a specific label. Forexample, dashed line 430 can be considered as an S1-MME signalingbearer, dashed line 434 can be considered as an S11 signaling bearer anddashed line 436 can be considered as an S6a signaling bearer, e.g.,according to LTE-EPS architecture standards. The above bearer paths andsignaling bearer paths are only illustrated as examples and it should benoted that additional bearer paths and signaling bearer paths may existthat are not illustrated.

Also shown is a novel user plane path/interface, referred to as theS1-U+ interface 466. In the illustrative example, the S1-U+ user planeinterface extends between the eNB 416 a and PGW 426. Notably, S1-U+path/interface does not include SGW 420, a node that is otherwiseinstrumental in configuring or managing packet forwarding between eNB416 a and one or more external networks 406 by way of PGW 426. Asdisclosed herein, the S1-U+ path/interface facilitates autonomouslearning of peer transport layer addresses by one or more of the networknodes to facilitate a self-configuring of the packet forwarding path. Inparticular, such self-configuring can be accomplished during handoversin most scenarios so as to reduce any extra signaling load on the S/PGWs420, 426 due to excessive handover events.

In some embodiments, PGW 426 is coupled to storage device 440, shown inphantom. Storage device 440 can be integral to one of the network nodes,such as PGW 426, for example, in the form of internal memory or diskdrive. It is understood that storage device 440 can include registerssuitable for storing address values. Alternatively or in addition,storage device 440 can be separate from PGW 426, for example, as anexternal hard drive, a flash drive, or network storage.

Storage device 440 selectively stores one or more values relevant to theforwarding of packet data. For example, storage device 440 can storeidentities or addresses of network entities, such as any of networknodes 418, 420, 422, 424, and 426, eNBs 416 or UE 414. In theillustrative example, storage device 440 includes a first storagelocation 442 and a second storage location 444. First storage location442 can be dedicated to storing a Currently Used Downlink address value442. Likewise, second storage location 444 can be dedicated to storing aDefault Downlink Forwarding address value 444. PGW 426 can read or writevalues into either of storage locations 442, 444, for example, managingCurrently Used Downlink Forwarding address value 442 and DefaultDownlink Forwarding address value 444 as disclosed herein.

In some embodiments, the Default Downlink Forwarding address for eachEPS bearer is the SGW S5-U address for each EPS Bearer. The CurrentlyUsed Downlink Forwarding address” for each EPS bearer in PGW 426 can beset every time when PGW 426 receives an uplink packet, e.g., a GTP-Uuplink packet, with a new source address for a corresponding EPS bearer.When UE 414 is in an idle state, the “Current Used Downlink Forwardingaddress” field for each EPS bearer of UE 414 can be set to a “null” orother suitable value.

In some embodiments, the Default Downlink Forwarding address is onlyupdated when PGW 426 receives a new SGW S5-U address in a predeterminedmessage or messages. For example, the Default Downlink Forwardingaddress is only updated when PGW 426 receives one of a Create SessionRequest, Modify Bearer Request and Create Bearer Response messages fromSGW 420.

As values 442, 444 can be maintained and otherwise manipulated on a perbearer basis, it is understood that the storage locations can take theform of tables, spreadsheets, lists, or other data structures generallywell understood and suitable for maintaining or otherwise manipulateforwarding addresses on a per bearer basis.

It should be noted that access network 402 and core network 404 areillustrated in a simplified block diagram in FIG. 4. In other words,either or both of access network 402 and the core network 404 caninclude additional network elements that are not shown, such as variousrouters, switches, and controllers. In addition, although FIG. 4illustrates only a single one of each of the various network elements,it should be noted that access network 402 and core network 404 caninclude any number of the various network elements. For example, corenetwork 404 can include a pool (i.e., more than one) of MMEs 418, SGWs420 or PGWs 426.

In the illustrative example, data traversing a network path between UE414, eNB 416 a, SGW 420, PGW 426 and external network 406 may beconsidered to constitute data transferred according to an end-to-end IPservice. However, for the present disclosure, to properly performestablishment management in LTE-EPS network architecture 400, the corenetwork, data bearer portion of the end-to-end IP service is analyzed.

An establishment may be defined herein as a connection set up requestbetween any two elements within LTE-EPS network architecture 400. Theconnection set up request may be for user data or for signaling. Afailed establishment may be defined as a connection set up request thatwas unsuccessful. A successful establishment may be defined as aconnection set up request that was successful.

In one embodiment, a data bearer portion comprises a first portion(e.g., a data radio bearer 446) between UE 414 and eNB 416 a, a secondportion (e.g., an S1 data bearer 428) between eNB 416 a and SGW 420, anda third portion (e.g., an S5/S8 bearer 432) between SGW 420 and PGW 426.Various signaling bearer portions are also illustrated in FIG. 4. Forexample, a first signaling portion (e.g., a signaling radio bearer 448)between UE 414 and eNB 416 a, and a second signaling portion (e.g., S1signaling bearer 430) between eNB 416 a and MME 418.

In at least some embodiments, the data bearer can include tunneling,e.g., IP tunneling, by which data packets can be forwarded in anencapsulated manner, between tunnel endpoints. Tunnels, or tunnelconnections can be identified in one or more nodes of network 400, e.g.,by one or more of tunnel endpoint identifiers, an IP address, and a userdatagram protocol port number. Within a particular tunnel connection,payloads, e.g., packet data, which may or may not include protocolrelated information, are forwarded between tunnel endpoints.

An example of first tunnel solution 450 includes a first tunnel 452 abetween two tunnel endpoints 454 a and 456 a, and a second tunnel 452 bbetween two tunnel endpoints 454 b and 456 b. In the illustrativeexample, first tunnel 452 a is established between eNB 416 a and SGW420. Accordingly, first tunnel 452 a includes a first tunnel endpoint454 a corresponding to an S1-U address of eNB 416 a (referred to hereinas the eNB S1-U address), and second tunnel endpoint 456 a correspondingto an S1-U address of SGW 420 (referred to herein as the SGW S1-Uaddress). Likewise, second tunnel 452 b includes first tunnel endpoint454 b corresponding to an S5-U address of SGW 420 (referred to herein asthe SGW S5-U address), and second tunnel endpoint 456 b corresponding toan S5-U address of PGW 426 (referred to herein as the PGW S5-U address).

In at least some embodiments, first tunnel solution 450 is referred toas a two tunnel solution, e.g., according to the GPRS Tunneling ProtocolUser Plane (GTPv1-U based), as described in 3GPP specification TS29.281, incorporated herein in its entirety. It is understood that oneor more tunnels are permitted between each set of tunnel end points. Forexample, each subscriber can have one or more tunnels, e.g., one foreach PDP context that they have active, as well as possibly havingseparate tunnels for specific connections with different quality ofservice requirements, and so on.

An example of second tunnel solution 458 includes a single or directtunnel 460 between tunnel endpoints 462 and 464. In the illustrativeexample, direct tunnel 460 is established between eNB 416 a and PGW 426,without subjecting packet transfers to processing related to SGW 420.Accordingly, direct tunnel 460 includes first tunnel endpoint 462corresponding to the eNB S1-U address, and second tunnel endpoint 464corresponding to the PGW S5-U address. Packet data received at eitherend can be encapsulated into a payload and directed to the correspondingaddress of the other end of the tunnel. Such direct tunneling avoidsprocessing, e.g., by SGW 420 that would otherwise relay packets betweenthe same two endpoints, e.g., according to a protocol, such as the GTP-Uprotocol.

In some scenarios, direct tunneling solution 458 can forward user planedata packets between eNB 416 a and PGW 426, by way of SGW 420. Forexample, SGW 420 can serve a relay function, by relaying packets betweentwo tunnel endpoints 416 a, 426. In other scenarios, direct tunnelingsolution 458 can forward user data packets between eNB 416 a and PGW426, by way of the S1 U+ interface, thereby bypassing SGW 420.

Generally, UE 414 can have one or more bearers at any one time. Thenumber and types of bearers can depend on applications, defaultrequirements, and so on. It is understood that the techniques disclosedherein, including the configuration, management and use of varioustunnel solutions 450, 458, can be applied to the bearers on anindividual basis. For example, if user data packets of one bearer, say abearer associated with a VoIP service of UE 414, then the forwarding ofall packets of that bearer are handled in a similar manner. Continuingwith this example, the same UE 414 can have another bearer associatedwith it through the same eNB 416 a. This other bearer, for example, canbe associated with a relatively low rate data session forwarding userdata packets through core network 404 simultaneously with the firstbearer. Likewise, the user data packets of the other bearer are alsohandled in a similar manner, without necessarily following a forwardingpath or solution of the first bearer. Thus, one of the bearers may beforwarded through direct tunnel 458; whereas, another one of the bearersmay be forwarded through a two-tunnel solution 450.

FIG. 5 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 500 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as processor 302, UE 414, eNB 416, MME 418, SGW420, HSS 422, PCRF 424, PGW 426 and other devices of FIGS. 1, 2, and 4.In some embodiments, the machine may be connected (e.g., using a network502) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client user machine in aserver-client user network environment, or as a peer machine in apeer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video, ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

Computer system 500 may include a processor (or controller) 504 (e.g., acentral processing unit (CPU)), a graphics processing unit (GPU, orboth), a main memory 506 and a static memory 508, which communicate witheach other via a bus 510. The computer system 500 may further include adisplay unit 512 (e.g., a liquid crystal display (LCD), a flat panel, ora solid-state display). Computer system 500 may include an input device514 (e.g., a keyboard), a cursor control device 516 (e.g., a mouse), adisk drive unit 518, a signal generation device 520 (e.g., a speaker orremote control) and a network interface device 522. In distributedenvironments, the embodiments described in the subject disclosure can beadapted to utilize multiple display units 512 controlled by two or morecomputer systems 500. In this configuration, presentations described bythe subject disclosure may in part be shown in a first of display units512, while the remaining portion is presented in a second of displayunits 512.

The disk drive unit 518 may include a tangible computer-readable storagemedium 524 on which is stored one or more sets of instructions (e.g.,software 526) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above.Instructions 526 may also reside, completely or at least partially,within main memory 506, static memory 508, or within processor 504during execution thereof by the computer system 500. Main memory 506 andprocessor 504 also may constitute tangible computer-readable storagemedia.

As shown in FIG. 6, telecommunication system 600 may include wirelesstransmit/receive units (WTRUs) 602, a RAN 604, a core network 606, apublic switched telephone network (PSTN) 608, the Internet 610, or othernetworks 612, though it will be appreciated that the disclosed examplescontemplate any number of WTRUs, base stations, networks, or networkelements. Each WTRU 602 may be any type of device configured to operateor communicate in a wireless environment. For example, a WTRU maycomprise IoT devices 32, a mobile device, network device 300, or thelike, or any combination thereof. By way of example, WTRUs 602 may beconfigured to transmit or receive wireless signals and may include a UE,a mobile station, a mobile device, a fixed or mobile subscriber unit, apager, a cellular telephone, a PDA, a smartphone, a laptop, a netbook, apersonal computer, a wireless sensor, consumer electronics, or the like.WTRUs 602 may be configured to transmit or receive wireless signals overan air interface 614.

Telecommunication system 600 may also include one or more base stations616. Each of base stations 616 may be any type of device configured towirelessly interface with at least one of the WTRUs 602 to facilitateaccess to one or more communication networks, such as core network 606,PTSN 608, Internet 610, or other networks 612. By way of example, basestations 616 may be a base transceiver station (BTS), a Node-B, aneNodeB, a Home Node B, a Home eNodeB, a site controller, an access point(AP), a wireless router, or the like. While base stations 616 are eachdepicted as a single element, it will be appreciated that base stations616 may include any number of interconnected base stations or networkelements.

RAN 604 may include one or more base stations 616, along with othernetwork elements (not shown), such as a base station controller (BSC), aradio network controller (RNC), or relay nodes. One or more basestations 616 may be configured to transmit or receive wireless signalswithin a particular geographic region, which may be referred to as acell (not shown). The cell may further be divided into cell sectors. Forexample, the cell associated with base station 616 may be divided intothree sectors such that base station 616 may include three transceivers:one for each sector of the cell. In another example, base station 616may employ multiple-input multiple-output (MIMO) technology and,therefore, may utilize multiple transceivers for each sector of thecell.

Base stations 616 may communicate with one or more of WTRUs 602 over airinterface 614, which may be any suitable wireless communication link(e.g., RF, microwave, infrared (IR), ultraviolet (UV), or visiblelight). Air interface 614 may be established using any suitable radioaccess technology (RAT).

More specifically, as noted above, telecommunication system 600 may be amultiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, or the like. Forexample, base station 616 in RAN 604 and WTRUs 602 connected to RAN 604may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA) thatmay establish air interface 614 using wideband CDMA (WCDMA). WCDMA mayinclude communication protocols, such as High-Speed Packet Access (HSPA)or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink PacketAccess (HSDPA) or High-Speed Uplink Packet Access (HSUPA).

As another example base station 616 and WTRUs 602 that are connected toRAN 604 may implement a radio technology such as Evolved UMTSTerrestrial Radio Access (E-UTRA), which may establish air interface 614using LTE or LTE-Advanced (LTE-A).

Optionally base station 616 and WTRUs 602 connected to RAN 604 mayimplement radio technologies such as IEEE 602.16 (i.e., WorldwideInteroperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1×,CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95(IS-95), Interim Standard 856 (IS-856), GSM, Enhanced Data rates for GSMEvolution (EDGE), GSM EDGE (GERAN), or the like.

Base station 616 may be a wireless router, Home Node B, Home eNodeB, oraccess point, for example, and may utilize any suitable RAT forfacilitating wireless connectivity in a localized area, such as a placeof business, a home, a vehicle, a campus, or the like. For example, basestation 616 and associated WTRUs 602 may implement a radio technologysuch as IEEE 602.11 to establish a wireless local area network (WLAN).As another example, base station 616 and associated WTRUs 602 mayimplement a radio technology such as IEEE 602.15 to establish a wirelesspersonal area network (WPAN). In yet another example, base station 616and associated WTRUs 602 may utilize a cellular-based RAT (e.g., WCDMA,CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell.As shown in FIG. 6, base station 616 may have a direct connection toInternet 610. Thus, base station 616 may not be required to accessInternet 610 via core network 606.

RAN 604 may be in communication with core network 606, which may be anytype of network configured to provide voice, data, applications, orvoice over internet protocol (VoIP) services to one or more WTRUs 602.For example, core network 606 may provide call control, billingservices, mobile location-based services, pre-paid calling, Internetconnectivity, video distribution or high-level security functions, suchas user authentication. Although not shown in FIG. 6, it will beappreciated that RAN 604 or core network 606 may be in direct orindirect communication with other RANs that employ the same RAT as RAN604 or a different RAT. For example, in addition to being connected toRAN 604, which may be utilizing an E-UTRA radio technology, core network606 may also be in communication with another RAN (not shown) employinga GSM radio technology.

Core network 606 may also serve as a gateway for WTRUs 602 to accessPSTN 608, Internet 610, or other networks 612. PSTN 608 may includecircuit-switched telephone networks that provide plain old telephoneservice (POTS). For LTE core networks, core network 606 may use IMS core614 to provide access to PSTN 608. Internet 610 may include a globalsystem of interconnected computer networks or devices that use commoncommunication protocols, such as the transmission control protocol(TCP), user datagram protocol (UDP), or IP in the TCP/IP internetprotocol suite. Other networks 612 may include wired or wirelesscommunications networks owned or operated by other service providers.For example, other networks 612 may include another core networkconnected to one or more RANs, which may employ the same RAT as RAN 604or a different RAT.

Some or all WTRUs 602 in telecommunication system 600 may includemulti-mode capabilities. For example, WTRUs 602 may include multipletransceivers for communicating with different wireless networks overdifferent wireless links. For example, one or more WTRUs 602 may beconfigured to communicate with base station 616, which may employ acellular-based radio technology, and with base station 616, which mayemploy an IEEE 802 radio technology.

FIG. 7 is an example system 700 including RAN 604 and core network 606.As noted above, RAN 604 may employ an E-UTRA radio technology tocommunicate with WTRUs 602 over air interface 614. RAN 604 may also bein communication with core network 606.

RAN 604 may include any number of eNodeBs 702 while remaining consistentwith the disclosed technology. One or more eNodeBs 702 may include oneor more transceivers for communicating with the WTRUs 602 over airinterface 614. Optionally, eNodeBs 702 may implement MIMO technology.Thus, one of eNodeBs 702, for example, may use multiple antennas totransmit wireless signals to, or receive wireless signals from, one ofWTRUs 602.

Each of eNodeBs 702 may be associated with a particular cell (not shown)and may be configured to handle radio resource management decisions,handover decisions, scheduling of users in the uplink or downlink, orthe like. As shown in FIG. 7 eNodeBs 702 may communicate with oneanother over an X2 interface.

Core network 606 shown in FIG. 7 may include a mobility managementgateway or entity (MME) 704, a serving gateway 706, or a packet datanetwork (PDN) gateway 708. While each of the foregoing elements aredepicted as part of core network 606, it will be appreciated that anyone of these elements may be owned or operated by an entity other thanthe core network operator.

MME 704 may be connected to each of eNodeBs 702 in RAN 604 via an S1interface and may serve as a control node. For example, MME 704 may beresponsible for authenticating users of WTRUs 602, bearer activation ordeactivation, selecting a particular serving gateway during an initialattach of WTRUs 602, or the like. MME 704 may also provide a controlplane function for switching between RAN 604 and other RANs (not shown)that employ other radio technologies, such as GSM or WCDMA.

Serving gateway 706 may be connected to each of eNodeBs 702 in RAN 604via the S1 interface. Serving gateway 706 may generally route or forwarduser data packets to or from the WTRUs 602. Serving gateway 706 may alsoperform other functions, such as anchoring user planes duringinter-eNodeB handovers, triggering paging when downlink data isavailable for WTRUs 602, managing or storing contexts of WTRUs 602, orthe like.

Serving gateway 706 may also be connected to PDN gateway 708, which mayprovide WTRUs 602 with access to packet-switched networks, such asInternet 610, to facilitate communications between WTRUs 602 andIP-enabled devices.

Core network 606 may facilitate communications with other networks. Forexample, core network 606 may provide WTRUs 602 with access tocircuit-switched networks, such as PSTN 608, such as through IMS core614, to facilitate communications between WTRUs 602 and traditionalland-line communications devices. In addition, core network 606 mayprovide the WTRUs 602 with access to other networks 612, which mayinclude other wired or wireless networks that are owned or operated byother service providers.

FIG. 8 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a GPRS network as describedherein. In the example packet-based mobile cellular network environmentshown in FIG. 8, there are a plurality of base station subsystems (BSS)800 (only one is shown), each of which comprises a base stationcontroller (BSC) 802 serving a plurality of BTSs, such as BTSs 804, 806,808. BTSs 804, 806, 808 are the access points where users ofpacket-based mobile devices become connected to the wireless network. Inexample fashion, the packet traffic originating from mobile devices istransported via an over-the-air interface to BTS 808, and from BTS 808to BSC 802. Base station subsystems, such as BSS 800, are a part ofinternal frame relay network 810 that can include a service GPRS supportnodes (SGSN), such as SGSN 812 or SGSN 814. Each SGSN 812, 814 isconnected to an internal packet network 816 through which SGSN 812, 814can route data packets to or from a plurality of gateway GPRS supportnodes (GGSN) 818, 820, 822. As illustrated, SGSN 814 and GGSNs 818, 820,822 are part of internal packet network 816. GGSNs 818, 820, 822 mainlyprovide an interface to external IP networks such as PLMN 824, corporateintranets/internets 826, or Fixed-End System (FES) or the publicInternet 828. As illustrated, subscriber corporate network 826 may beconnected to GGSN 820 via a firewall 830. PLMN 824 may be connected toGGSN 820 via a boarder gateway router (BGR) 832. A Remote AuthenticationDial-In User Service (RADIUS) server 834 may be used for callerauthentication when a user calls corporate network 826.

Generally, there may be a several cell sizes in a network, referred toas macro, micro, pico, femto or umbrella cells. The coverage area ofeach cell is different in different environments. Macro cells can beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro cells aretypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells are used mainly indoors.Femto cells have the same size as pico cells, but a smaller transportcapacity. Femto cells are used indoors, in residential or small businessenvironments. On the other hand, umbrella cells are used to covershadowed regions of smaller cells and fill in gaps in coverage betweenthose cells.

FIG. 9 illustrates an architecture of a typical GPRS network 900 asdescribed herein. The architecture depicted in FIG. 9 may be segmentedinto four groups: users 902, RAN 904, core network 906, and interconnectnetwork 908. Users 902 comprise a plurality of end users, who each mayuse one or more devices 910. Note that device 910 is referred to as amobile subscriber (MS) in the description of network shown in FIG. 9. Inan example, device 910 comprises a communications device (e.g., IoTdevices 32, mobile positioning center 116, network device 300, any ofdetected devices 500, second device 508, access device 604, accessdevice 606, access device 608, access device 610 or the like, or anycombination thereof). Radio access network 904 comprises a plurality ofBSSs such as BSS 912, which includes a BTS 914 and a BSC 916. Corenetwork 906 may include a host of various network elements. Asillustrated in FIG. 9, core network 906 may comprise MSC 918, servicecontrol point (SCP) 920, gateway MSC (GMSC) 922, SGSN 924, home locationregister (HLR) 926, authentication center (AuC) 928, domain name system(DNS) server 930, and GGSN 932. Interconnect network 908 may alsocomprise a host of various networks or other network elements. Asillustrated in FIG. 9, interconnect network 908 comprises a PSTN 934, aFES/Internet 936, a firewall 1038, or a corporate network 940.

An MSC can be connected to a large number of BSCs. At MSC 918, forinstance, depending on the type of traffic, the traffic may be separatedin that voice may be sent to PSTN 934 through GMSC 922, or data may besent to SGSN 924, which then sends the data traffic to GGSN 932 forfurther forwarding.

When MSC 918 receives call traffic, for example, from BSC 916, it sendsa query to a database hosted by SCP 920, which processes the request andissues a response to MSC 918 so that it may continue call processing asappropriate.

HLR 926 is a centralized database for users to register to the GPRSnetwork. HLR 926 stores static information about the subscribers such asthe International Mobile Subscriber Identity (IMSI), subscribedservices, or a key for authenticating the subscriber. HLR 926 alsostores dynamic subscriber information such as the current location ofthe MS. Associated with HLR 926 is AuC 928, which is a database thatcontains the algorithms for authenticating subscribers and includes theassociated keys for encryption to safeguard the user input forauthentication.

In the following, depending on context, “mobile subscriber” or “MS”sometimes refers to the end user and sometimes to the actual portabledevice, such as a mobile device, used by an end user of the mobilecellular service. When a mobile subscriber turns on his or her mobiledevice, the mobile device goes through an attach process by which themobile device attaches to an SGSN of the GPRS network. In FIG. 9, whenMS 910 initiates the attach process by turning on the networkcapabilities of the mobile device, an attach request is sent by MS 910to SGSN 924. The SGSN 924 queries another SGSN, to which MS 910 wasattached before, for the identity of MS 910. Upon receiving the identityof MS 910 from the other SGSN, SGSN 924 requests more information fromMS 910. This information is used to authenticate MS 910 together withthe information provided by HLR 926. Once verified, SGSN 924 sends alocation update to HLR 926 indicating the change of location to a newSGSN, in this case SGSN 924. HLR 926 notifies the old SGSN, to which MS910 was attached before, to cancel the location process for MS 910. HLR926 then notifies SGSN 924 that the location update has been performed.At this time, SGSN 924 sends an Attach Accept message to MS 910, whichin turn sends an Attach Complete message to SGSN 924.

Next, MS 910 establishes a user session with the destination network,corporate network 940, by going through a Packet Data Protocol (PDP)activation process. Briefly, in the process, MS 910 requests access tothe Access Point Name (APN), for example, UPS.com, and SGSN 924 receivesthe activation request from MS 910. SGSN 924 then initiates a DNS queryto learn which GGSN 932 has access to the UPS.com APN. The DNS query issent to a DNS server within core network 906, such as DNS server 930,which is provisioned to map to one or more GGSNs in core network 906.Based on the APN, the mapped GGSN 932 can access requested corporatenetwork 940. SGSN 924 then sends to GGSN 932 a Create PDP ContextRequest message that contains necessary information. GGSN 932 sends aCreate PDP Context Response message to SGSN 924, which then sends anActivate PDP Context Accept message to MS 910.

Once activated, data packets of the call made by MS 910 can then gothrough RAN 904, core network 906, and interconnect network 908, in aparticular FES/Internet 936 and firewall 1038, to reach corporatenetwork 940.

FIG. 10 illustrates a PLMN block diagram view of an example architecturethat may be replaced by a telecommunications system. In FIG. 10, solidlines may represent user traffic signals, and dashed lines may representsupport signaling. MS 1002 is the physical equipment used by the PLMNsubscriber. For example, IoT devices 32, network device 300, the like,or any combination thereof may serve as MS 1002. MS 1002 may be one of,but not limited to, a cellular telephone, a cellular telephone incombination with another electronic device or any other wireless mobilecommunication device.

MS 1002 may communicate wirelessly with BSS 1004. BSS 1004 contains BSC1006 and a BTS 1008. BSS 1004 may include a single BSC 1006/BTS 1008pair (base station) or a system of BSC/BTS pairs that are part of alarger network. BSS 1004 is responsible for communicating with MS 1002and may support one or more cells. BSS 1004 is responsible for handlingcellular traffic and signaling between MS 1002 and a core network 1010.Typically, BSS 1004 performs functions that include, but are not limitedto, digital conversion of speech channels, allocation of channels tomobile devices, paging, or transmission/reception of cellular signals.

Additionally, MS 1002 may communicate wirelessly with RNS 1012. RNS 1012contains a Radio Network Controller (RNC) 1014 and one or more Nodes B1016. RNS 1012 may support one or more cells. RNS 1012 may also includeone or more RNC 1014/Node B 1016 pairs or alternatively a single RNC1014 may manage multiple Nodes B 1016. RNS 1012 is responsible forcommunicating with MS 1002 in its geographically defined area. RNC 1014is responsible for controlling Nodes B 1016 that are connected to it andis a control element in a UMTS radio access network. RNC 1014 performsfunctions such as, but not limited to, load control, packet scheduling,handover control, security functions, or controlling MS 1002 access tocore network 1010.

An E-UTRA Network (E-UTRAN) 1018 is a RAN that provides wireless datacommunications for MS 1002 and UE 1024. E-UTRAN 1018 provides higherdata rates than traditional UMTS. It is part of the LTE upgrade formobile networks, and later releases meet the requirements of theInternational Mobile Telecommunications (IMT) Advanced and are commonlyknown as a 4G networks. E-UTRAN 1018 may include of series of logicalnetwork components such as E-UTRAN Node B (eNB) 1020 and E-UTRAN Node B(eNB) 1022. E-UTRAN 1018 may contain one or more eNBs. User equipment(UE) 1024 may be any mobile device capable of connecting to E-UTRAN 1018including, but not limited to, a personal computer, laptop, mobiledevice, wireless router, or other device capable of wirelessconnectivity to E-UTRAN 1018. The improved performance of the E-UTRAN1018 relative to a typical UMTS network allows for increased bandwidth,spectral efficiency, and functionality including, but not limited to,voice, high-speed applications, large data transfer or IPTV, while stillallowing for full mobility.

Typically, MS 1002 may communicate with any or all of BSS 1004, RNS1012, or E-UTRAN 1018. In an illustrative system, each of BSS 1004, RNS1012, and E-UTRAN 1018 may provide MS 1002 with access to core network1010. Core network 1010 may include of a series of devices that routedata and communications between end users. Core network 1010 may providenetwork service functions to users in the circuit switched (CS) domainor the packet switched (PS) domain. The CS domain refers to connectionsin which dedicated network resources are allocated at the time ofconnection establishment and then released when the connection isterminated. The PS domain refers to communications and data transfersthat make use of autonomous groupings of bits called packets. Eachpacket may be routed, manipulated, processed, or handled independentlyof all other packets in the PS domain and does not require dedicatednetwork resources.

The circuit-switched MGW function (CS-MGW) 1026 is part of core network1010 and interacts with VLR/MSC server 1028 and GMSC server 1030 inorder to facilitate core network 1010 resource control in the CS domain.Functions of CS-MGW 1026 include, but are not limited to, mediaconversion, bearer control, payload processing or other mobile networkprocessing such as handover or anchoring. CS-MGW 1026 may receiveconnections to MS 1002 through BSS 1004 or RNS 1012.

SGSN 1032 stores subscriber data regarding MS 1002 in order tofacilitate network functionality. SGSN 1032 may store subscriptioninformation such as, but not limited to, the IMSI, temporary identities,or PDP addresses. SGSN 1032 may also store location information such as,but not limited to, GGSN address for each GGSN 1034 where an active PDPexists. GGSN 1034 may implement a location register function to storesubscriber data it receives from SGSN 1032 such as subscription orlocation information.

Serving gateway (S-GW) 1036 is an interface which provides connectivitybetween E-UTRAN 1018 and core network 1010. Functions of S-GW 1036include, but are not limited to, packet routing, packet forwarding,transport level packet processing, or user plane mobility anchoring forinter-network mobility. PCRF 1038 uses information gathered from P-GW1036, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources or other networkadministration functions. PDN gateway (PDN-GW) 1040 may provideuser-to-services connectivity functionality including, but not limitedto, GPRS/EPC network anchoring, bearer session anchoring and control, orIP address allocation for PS domain connections.

HSS 1042 is a database for user information and stores subscription dataregarding MS 1002 or UE 1024 for handling calls or data sessions.Networks may contain one HSS 1042 or more if additional resources arerequired. Example data stored by HSS 1042 include, but is not limitedto, user identification, numbering or addressing information, securityinformation, or location information. HSS 1042 may also provide call orsession establishment procedures in both the PS and CS domains.

VLR/MSC Server 1028 provides user location functionality. When MS 1002enters a new network location, it begins a registration procedure. AnMSC server for that location transfers the location information to theVLR for the area. A VLR and MSC server may be located in the samecomputing environment, as is shown by VLR/MSC server 1028, oralternatively may be located in separate computing environments. A VLRmay contain, but is not limited to, user information such as the IMSI,the Temporary Mobile Station Identity (TMSI), the Local Mobile StationIdentity (LMSI), the last known location of the mobile station, or theSGSN where the mobile station was previously registered. The MSC servermay contain information such as, but not limited to, procedures for MS1002 registration or procedures for handover of MS 1002 to a differentsection of core network 1010. GMSC server 1030 may serve as a connectionto alternate GMSC servers for other MSs in larger networks.

EIR 1044 is a logical element which may store the IMEI for MS 1002. Userequipment may be classified as either “white listed” or “black listed”depending on its status in the network. If MS 1002 is stolen and put touse by an unauthorized user, it may be registered as “black listed” inEIR 1044, preventing its use on the network. An MME 1046 is a controlnode which may track MS 1002 or UE 1024 if the devices are idle.Additional functionality may include the ability of MME 1046 to contactidle MS 1002 or UE 1024 if retransmission of a previous session isrequired.

As described herein, a telecommunications system may include a coresimulation tool (CST) having a software defined engine (SDE) that cancreate an analytics environment(s) within an evolved packet core (EPC).The proposed analytics environment may be used to create analyticaldatabases and run associated analytic tools within boundaries of theEPC. An advantage of the proposed telecommunications system is that anetwork carrier would be able to establish multiple analyticsenvironments for each customer or multiple customers as required withoutleaving the EPC boundaries thereby creating greater efficiencies,performance, security, and control by the network carrier. The proposedanalytics environment may also provide a greater degree of granularityinto the operation of a customer's environment or the telecommunicationsnetwork in general. For example, an analytical engine within the EPCcore may be able to associate data with individual IoT sensors withinthe customer's environment, a location for each of these sensors withinthe customer's environment, and other performance and securityinformation, which exists within an EPC core of the network carrier.

In addition to analyzing sensor data, the proposed analytics environmentmay be used to capture and analyze a Radio Access Network (RAN)utilization and performance. Data may be collected from RAN networkelements (e.g., eNodeBs) for analysis. Accordingly, an internal networkelement (CST) internal to the EPC may be used to analyze RAN data, aswell as and combine the RAN data with subscriber information, deviceinformation, location information, and security information. Byanalyzing RAN data in conjunction with data gleaned from networkelements internal to the EPC, a finer granularity of network performancecan be obtained.

The analysis by the CST can cause alerts to be generated (e.g., inresponse to network performance issues), cause network optimizations(e.g., installation/removal of macro sites, small cells, etc.) inresponse to a determination of coverage gaps within a customer premiseor within the telecommunications network in general, and dynamicallyadjust network parameters of the EPC core to improve networkperformance.

While examples of described telecommunications system have beendescribed in connection with various computing devices/processors, theunderlying concepts may be applied to any computing device, processor,or system capable of facilitating a telecommunications system. Thevarious techniques described herein may be implemented in connectionwith hardware or software or, where appropriate, with a combination ofboth. Thus, the methods and devices may take the form of program code(i.e., instructions) embodied in concrete, tangible, storage mediahaving a concrete, tangible, physical structure. Examples of tangiblestorage media include floppy diskettes, CD-ROMs, DVDs, hard drives, orany other tangible machine-readable storage medium (computer-readablestorage medium). Thus, a computer-readable storage medium is not asignal. A computer-readable storage medium is not a transient signal.Further, a computer-readable storage medium is not a propagating signal.A computer-readable storage medium as described herein is an article ofmanufacture. When the program code is loaded into and executed by amachine, such as a computer, the machine becomes a device fortelecommunications. In the case of program code execution onprogrammable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile or nonvolatile memory or storage elements), at least one inputdevice, and at least one output device. The program(s) can beimplemented in assembly or machine language, if desired. The languagecan be a compiled or interpreted language, and may be combined withhardware implementations.

The methods and devices associated with a telecommunications system asdescribed herein also may be practiced via communications embodied inthe form of program code that is transmitted over some transmissionmedium, such as over electrical wiring or cabling, through fiber optics,or via any other form of transmission, wherein, when the program code isreceived and loaded into and executed by a machine, such as an EPROM, agate array, a programmable logic device (PLD), a client computer, or thelike, the machine becomes an device for implementing telecommunicationsas described herein. When implemented on a general-purpose processor,the program code combines with the processor to provide a unique devicethat operates to invoke the functionality of a telecommunicationssystem.

While a telecommunications system has been described in connection withthe various examples of the various figures, it is to be understood thatother similar implementations may be used or modifications and additionsmay be made to the described examples of a telecommunications systemwithout deviating therefrom. For example, one skilled in the art willrecognize that a telecommunications system as described in the instantapplication may apply to any environment, whether wired or wireless, andmay be applied to any number of such devices connected via acommunications network and interacting across the network. Therefore, atelecommunications system as described herein should not be limited toany single example, but rather should be construed in breadth and scopein accordance with the appended claims.

What is claimed:
 1. A device comprising: a processor; and a memorycoupled with the processor, the memory storing executable instructionsthat when executed by the processor, cause the processor to effectuateoperations comprising: deploying a user plane virtual network functionin one or more customer premise equipment (CPE) devices of a CPE networkof a plurality of CPE networks within a telecommunications network,wherein the user plane virtual network function receives sensor dataassociated with the one or more CPE devices and transmits the sensordata to a core simulation tool, and wherein the user plane virtualnetwork function performs analytics on the sensor data of the one ormore CPE devices within the CPE network; based on the analytics on thesensor data, determining a status of the CPE network; and based on thestatus of the CPE network, performing an action to optimize the CPEnetwork.
 2. The device of claim 1, wherein the one or more CPE devicescomprises one or more Internet-of-things (IoT) devices.
 3. The device ofclaim 1, wherein the one or more CPE devices comprises one or moreInternet-of-things (IoT) devices, wherein the one or more IoT devicescomprise smart meters.
 4. The device of claim 1, wherein the one or moreCPE devices comprises one or more Internet-of-things (IoT) devices,wherein the one or more IoT devices comprise weather monitoring systemsensors.
 5. The device of claim 1, wherein the one or more CPE devicescomprises one or more Internet-of-things (IoT) devices, wherein thesensor data comprises location data for each of the IoT devices.
 6. Thedevice of claim 1, wherein the action to optimize the CPE networkcomprises reducing collection of the sensor data from the CPE network.7. The device of claim 1, wherein the action to optimize the CPE networkis based on usage pattern changes for the one or more CPE devices. 8.The device of claim 1, wherein the analytics performed on the sensordata is used to detect network coverage gaps at designated locationswithin the CPE network.
 9. The device of claim 1, wherein the action tooptimize the CPE network comprises adjusting network performanceparameters of a core network of the telecommunications network.
 10. Amethod comprising: deploying, by a processing system comprising aprocessor, a user plane virtual network function at a designatedlocation within a customer premise equipment (CPE) network of atelecommunications network; receiving, by the user plane virtual networkfunction, sensor data associated with one or more CPE device in the CPEnetwork; performing, by the user plane virtual network function,analytics on the sensor data of the one or more CPE devices within theCPE network; based on the analytics on the sensor data, determining, bythe user plane virtual network function, a status of the CPE network;and based on the status of the CPE network, performing, by the userplane virtual network function, an action to optimize the CPE network.11. The method of claim 10, wherein the one or more CPE devicescomprises one or more Internet-of-things (IoT) devices.
 12. The methodof claim 10, wherein the one or more CPE devices comprises one or moreInternet-of-things (IoT) devices, wherein the one or more IoT devicescomprise smart meters.
 13. The method of claim 12, wherein the one ormore IoT devices comprise weather monitoring system sensors.
 14. Themethod of claim 10, wherein the action to optimize the CPE networkcomprises reducing collection of the sensor data from the CPE network.15. The method of claim 10, wherein the action to optimize the CPEnetwork is based on usage pattern changes for the one or more CPEdevices.
 16. The method of claim 10, wherein the analytics performed onthe sensor data is used to detect network coverage gaps at thedesignated location within the CPE network.
 17. The method of claim 10,wherein the action to optimize the CPE network comprises adjustingnetwork performance parameters of a core network of thetelecommunications network.
 18. A computer-readable storage mediumstoring executable instructions that when executed by a computing devicecause said computing device to effectuate operations comprising:implementing a user plane virtual network function at a designatedlocation within a customer premise equipment (CPE) network, wherein theCPE network is a portion of a telecommunications network; the user planevirtual network function receiving sensor data associated with one ormore CPE devices of the CPE portion; the user plane virtual networkfunction performing analytics on the sensor data of the one or more CPEdevices; based on analytics on the sensor data, the user plane virtualnetwork function determining a status of the CPE network; and based onthe status of the CPE network, the user plane virtual network functionperforming an action to optimize the CPE network.
 19. Thecomputer-readable storage medium of claim 18, wherein the analyticsperformed on the sensor data is used to detect network coverage gaps atthe designated location within the CPE network.
 20. Thecomputer-readable storage medium of claim 18, wherein the action tooptimize the CPE network comprises adjusting network performanceparameters of a core network of the telecommunications network.